This chapter gives procedures and commands for important Network Utility operations. It serves as a supplement to some of the concept presentations in previous chapters.
This section supplements the background information on event logging and viewing provided in Event Logging (Using talk 2, the Monitor Process) and Monitoring Event Messages. It introduces the commands that control what events are logged, and where they are logged.
You must use the command-line interface to activate event logging. From the Configuration Program, you can configure only general remote logging parameters.
From either the main talk 5 or talk 6 prompt, type event to enter the ELS Console or Config subprocess, respectively. You see essentially the same commands whether you are working under talk 5 or talk 6. Talk 5 ELS commands take effect immediately and are quite useful for turning on messages to debug a particular flow in a running system. From talk 6, you configure the events you want to be logged all the time, so you do not have to activate them each time you reboot the Network Utility.
There are six basic commands for activating and deactivating event logging, two for each of the three possible destinations of log messages:
All of these commands use the same method for specifying which events are to be activated or deactivated. Following the name of the command on the command line, you normally type one of the following (there are other options):
subsystem is the name of a functional component as known to ELS, such as "dls" for DLSw or "esc" for ESCON. You can type li sub to get a list of ELS subsystem names.
event# is the number of a predefined event, typed with leading zeros. You can type li sub subsystem to get a quick list of the events in a particular subsystem.
subsystem is the ELS subsystem name described above. The value "all" selects all subsystems.
logging_level is optional and defaults to "standard", which includes all error and unusual informational messages. The value "all" selects all messages in the subsystem.
The following list gives a few examples of these commands:
For detailed information about these commands, how to configure remote logging, what the logging levels are, and more, refer to "Using the Event Logging System (ELS)" in the MAS Software User's Guide.
This section describes how Network Utility memory is used, and how you can monitor its status.
A Network Utility ships with either 256 MB or 512 MB of main memory. When you boot the system, it loads operational code from disk into this memory, taking a certain amount of memory space for each load module. Once the operational code is loaded, the system splits up the remaining memory between APPN/TN3270 (if configured) and the routing function. The routing function includes IP, DLSw, TCP, channel gateway; in short, every function except APPN and TN3270 server.
When you configure APPN either from the Configuration Program or the command line, you can specify the amount of memory to be reserved for APPN. In Network Utility, this value is preset to the memory required for a maximum TN3270E server configuration12. This value should be reasonable for non-TN3270 APPN applications as well, so you should not need to change it. If your configuration does not enable APPN, Network Utility ignores the configured value and does not reserve memory for APPN. If your configuration enables APPN, Network Utility allocates the specified amount of memory to APPN and then allocates all remaining memory to the routing function.
You can monitor memory utilization in a running Network Utility either from a command-line console or from an SNMP management station. Either way, you look separately at the status of APPN memory and the status of routing function memory. Once the system is loaded, these memory partitions are fixed and are managed independently.
To monitor routing function memory from the command line:
To monitor APPN/TN3270 memory from the command line:
Network Utility supports IBM enterprise-specific MIBs that provide access to memory utilization information both for the routing function and for APPN/TN3270.
The Nways Manager products discussed in IBM Nways Manager Products provide full statistical support for both the APPN and routing function memory partitions. For either partition, you can view real-time and historical utilization information. You can set up alarm thresholds for either utilization percentage, so you can be notified when memory utilization reaches a certain level.
You can also configure Network Utility from the command line to send an SNMP trap when available routing function memory falls below a given threshold. From the talk 6 prompt Config>, type the command patch mosheap-lowmark and give the percentage value if you want to change it from the default value of 10%.
This section describes how to control CPU monitoring, and get reports from talk 5 or direct periodic messages to the talk 2 log.
From either the main talk 5 or talk 6 prompt, type perf to enter the Performance Monitoring Console or Config subprocess, respectively. From talk 6 and from the Configuration Program, you can enable or disable CPU utilization monitoring and set its operating parameters as part of your Network Utility configuration. From talk 5, you can make the same changes take effect immediately, and you can get reports on the CPU utilization in a running Network Utility.
Once you are at the PERF Console> prompt, the following commands are available to you:
All the same commands or parameters are available from talk 6 and the Configuration Program, except for clear and report.
For more information on these commands and examples of their output, see "Configuring and Monitoring Performance" in the MAS Software User's Guide.
Network Utility supports an IBM enterprise-specific MIB that provides access to current and historical CPU utilization information.
The Nways Manager products discussed in IBM Nways Manager Products provide full statistical support for Network Utility CPU utilization. You can view both real-time and historical utilization information. You can set up alarm thresholds for the utilization percentage, so you can be notified when it reaches a certain level.